Skip to content

feat: Next.js 16 update #2054

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 10 commits into from
Oct 22, 2025
Merged

feat: Next.js 16 update #2054

merged 10 commits into from
Oct 22, 2025
+2,243 −1,363

Conversation

@amannn
Copy link
Owner

@amannn amannn commented Oct 10, 2025 •
edited
Loading

Changes

  • Bump peer dependency for Next.js 16
  • Update examples for Next.js 16
  • Update docs to cover proxy.ts

🌐 learn.next-intl.dev has been updated for Next.js 16 as well (changelog)

@vercel
Copy link

vercel bot commented Oct 10, 2025 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
next-intl-docs Ready Ready Preview Comment Oct 22, 2025 8:06am
next-intl-example-app-router Ready Ready Preview Comment Oct 22, 2025 8:06am
next-intl-example-app-router-without-i18n-routing Ready Ready Preview Comment Oct 22, 2025 8:06am

@amannn amannn mentioned this pull request Oct 14, 2025
Open
@amannn amannn changed the title docs: Update examples to Next.js 16 feat: Next.js 16 update Oct 16, 2025
@l-you
Copy link

l-you commented Oct 18, 2025 •
edited
Loading

@amannn
I upgraded my app to Next.js 16.
Website and localisation works, BUT logs are polluted.

 ⨯ Error: Cannot find module '../../dictionaries/_next.json'
    at moduleContext (.next/server/chunks/ssr/[turbopack]_runtime.js:259:19)
    at moduleContext.import (.next/server/chunks/ssr/[turbopack]_runtime.js:275:22)
    at Module.D [as generateMetadata] (.next/server/chunks/ssr/_37fe6ccb._.js:2:22595) {
  code: 'MODULE_NOT_FOUND',
  digest: '4171074594'
}

Any idea what could cause it?
This is part of code in getRequestConfig. Seems like next-intl/plugin pass _next URL path of static file to the getRequestConfig locale property.

@amannn
Copy link
Owner Author

amannn commented Oct 20, 2025

Hmm, no—I haven't seen that when upgrading the examples here. No idea where _next is coming from, sorry!

@l-you
Copy link

l-you commented Oct 20, 2025

@amannn I'll try to create a reproducible nextjs app example.

@sss-Mihail-sss
Copy link

Next.js 16 is now stable :)
https://nextjs.org/blog/next-16

@amannn amannn marked this pull request as ready for review October 22, 2025 08:15
@amannn amannn merged commit c397e92 into main Oct 22, 2025
8 checks passed
@amannn amannn mentioned this pull request Oct 22, 2025
Closed
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@amannn @l-you @sss-Mihail-sss